Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1017

reference: 446-tree-1
name: 1017
tree-preservation-order: undefined
446-tpo-1
uprn
address-text
point: POINT (-1.023878 50.897641)
geometry: MULTIPOLYGON (((-1.023864 50.897640,-1.023866 50.897645,-1.023878 50.897649,-1.023886 50.897647,-1.023892 50.897643,-1.023892 50.897637,-1.023883 50.897631,-1.023874 50.897631,-1.023867 50.897634,-1.023864 50.897640)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL